Repository navigation
ci: release on every push to main - #30
Merged
Merged
Conversation
A merge to main now publishes: release.yml runs on push to main (and manual dispatch) instead of release/** branches, and the eligibility policy is ReleaseOnMain. The tool still decides per push: a package.json version with no v<version> tag is published to nuget.org and tagged with a GitHub release; an already-released version is skipped (REL002), so a merge without a version bump publishes nothing. Release runs are no longer cancelled in flight, because a run cancelled between publishing and tagging would leave a published version with no tag. The workflow file name, which the nuget.org Trusted Publishing policy is registered against, is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases now publish when a
package.jsonversion bump is merged intomain, instead of needing arelease/**branch.Important
Merging this PR publishes
1.0.0-prerelease.14to nuget.org.mainalready carries that version and it has no tag yet; a localrelease-explainwithGITHUB_REF=refs/heads/maingives Verdict: Release (REL001–REL003 pass). If you don't want .14 published yet, bumppackage.jsonin this PR first, or merge it when you're ready to ship .14.Changes
release.yml: triggers onpush: main(and manual dispatch) instead ofrelease/**.cancel-in-progress: false: a release cancelled between publishing and tagging would leave a version on nuget.org with no tag or GitHub release, so a later merge now queues instead..config/purview-build.jsonchanges fromTrunkReservesMinortoReleaseOnMain, the tool's default. Without this the tool treatsmainas a trunk it doesn't publish from, and changing the trigger alone would only ever produceSkip.REL002) and finishes green.release.yml, which is unchanged.Release-Flow.md, AGENTS.md and thepr.ymlcomment now describe the merge-to-release flow; the release-branch instructions are removed.Validation
actionlintpasses.purview-build release-explainwithReleaseOnMainonrefs/heads/maingives: Release.